Clarify cache access in Handle Fetch #1786
Conversation
The previous wording "the registration’s storage key’s name to cache map" was ambiguous. This change clarifies the mechanism for accessing caches during a fetch event handled by a service worker. Specifically, it replaces the ambiguous phrase with a direct call to "obtain a local storage bottle map" from the Storage specification, using the reserved client's environment. This makes the process of retrieving the cache map explicit and aligns the specification with modern storage standards. This addresses the issue raised in w3c#1784
|
@annevk Will you take a look? |
|
@sisidovski @domenic Upon #1784, I fixed the sentences on looking up the cache for the SW static routing API. It has been changed to use "obtain a local storage bottle map" in the storage specification, and uses reserved client as an environment. |
|
How is this related to whatwg/storage#185? |
This PR is the scenario without the change. |
Co-authored-by: Domenic Denicola <[email protected]>
The previous wording "the registration’s storage key’s name to cache map" was ambiguous. This change clarifies the mechanism for accessing caches during a fetch event handled by a service worker.
Specifically, it replaces the ambiguous phrase with a direct call to "obtain a local storage bottle map" from the Storage specification, using the reserved client's environment. This makes the process of retrieving the cache map explicit and aligns the specification with modern storage standards.
This addresses the issue raised in #1784
Preview | Diff